fix: nosubmit runs with default cluster config #34
+70
−25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses the following issues #30 and #32 and possibly impacts #28.
there were two problems here:
nosubmit
was different between the GMX and non-GMX config parsers. This was a simple fix and addresses cli-abfe -nosubmit #32nosubmit
the cluster configuration dictionary was set toNone
which raised an error in theScheduler.generate_scheduler_file
method.To fix (2) I've taken a guess at what you've intended and what is sensible and made the smallest change I could. Now the
nosubmit
flag has no influence on the generation of a cluster configuration.So now
nosubmit
will generate cluster config files taking into account thenumber_of_parallel_ligand_jobs
andnogpu
flags.I've also made some edits to the
gitignore
file for the outputs from the examples